-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config compiler #304
Config compiler #304
Conversation
We were treating configuration files in the project's config directory like normal elixir source files, but they're slightly different, and compiling them will cause errors to appear. This change adds a config compiler that uses Config.Reader to compile configuration. Fixes #301
I wasn't using Code.with_diagnostics, and was getting the dreaded "errors have been logged" message
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tested this branch in some projects and found that the config folder
under umbrella is not recognized, or using import_config "#{config_env()}.exs"
is also problematic, but I think it might be a result of incorrect configuration.
What do you mean? Errors are emitted just fine in the lexical project. |
Sorry, maybe I didn't explain it clearly enough. What I meant was that some So never mind. |
We were treating configuration files in the project's config directory
like normal elixir source files, but they're slightly different, and
compiling them will cause errors to appear.
This change adds a config compiler that uses Config.Reader to compile
configuration.
Fixes #301